Power transfer unit maintenance

ABSTRACT

A system is described, as well as methods of using the system. The method may include: determining at least one of the following: a communication error, a read-memory error, or an absence of a PTU shift between a two-wheel drive (2WD) mode and an all-wheel drive (AWD) mode for a threshold amount of vehicle operation; determining that a vehicle ignition state is not in a RUN state; and executing the task.

BACKGROUND

In two-wheel drive vehicles, a powertrain system of a vehicle may becoupled to one drive axle to deliver torque to the wheels thereof. In atleast some all-wheel drive vehicles, a power transfer unit mayselectively engage a second drive axle so that, when engaged, torque canbe delivered to four wheels rather than just two wheels. When the powertransfer unit is not used for a period of time, actuation componentswithin the PTU may become stuck or inoperable, thereby unable tofunction as required.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic view of a vehicle powertrain system.

FIG. 1A is a schematic view of an example of an actuator for apower-transfer unit in the system.

FIG. 2 is an electrical schematic view of a portion of the powertrainsystem shown in FIG. 1.

FIGS. 3-6 comprise a flow diagram illustrating a process for performingon-board maintenance for the system.

DETAILED DESCRIPTION

A powertrain system for a vehicle is described that includes a vehicledriveline system; one or more methods of using the vehicle drivelinesystem(s) are also described. According to one illustrative example, amethod for determining whether to execute a power transfer unit (PTU)maintenance task includes: determining at least one of the following: acommunication error, a read-memory error, or an absence of a PTU shiftbetween a two-wheel drive (2WD) mode and an all-wheel drive (AWD) modefor a threshold amount of vehicle operation; determining that a vehicleignition state is not in a RUN state; and based on both determinations,executing the task. Examples of vehicle operation include a distancetraveled during an ignition cycle or a global operation time, asdescribed below.

According to at least one example of the method, the task comprisesmoving actuator components of the PTU.

According to at least one example of the method, the task comprisesmoving a driving member of the actuator of the PTU relative to a drivenmember.

According to at least one example of the method, the threshold amount ofvehicle operation comprises either measuring vehicle travel distance ora global operation time.

According to at least one example of the method, the method furthercomprises: based on executing the task: resetting a distance counterthat measures vehicle mileage, resetting a counter associated with theglobal operation time, or both.

According to at least one example of the method, the method furthercomprises: executing the task during an extended_ON mode which provideselectrical power for a computer processor when the ignition state is anOFF or an accessory (ACC) state.

According to at least one example of the method, the method furthercomprises: aborting the task based on determining a change in theignition state or a PTU failure mode.

According to at least one example of the method, the method furthercomprises: storing an indication of a PTU maintenance event innon-volatile memory so that the task may be executed in response to asubsequent ignition cycle.

According to at least one example of the method, the communication errorcomprises one of: a connection failure, a node failure, or an errormessage over a communication network connection.

According to at least one example of the method, the read-memory errorcomprises one of: an inability of a computer processor to read datastored in computer memory; a memory error message indicating that atleast a portion of the computer memory is corrupted; or reading datafrom the computer memory, and determining that one or more data valuesare out-of-range.

According to at least one example of the method, the absence of the PTUshift between the 2WD mode and the AWD mode for the threshold amount ofvehicle operation comprises one of: (a) comparing a distance countervalue (ΔOV) with a mileage threshold, wherein the distance counter value(ΔOV) comprises a difference of a current odometer value (COV) and areset odometer value (ROV); or (b) comparing a global operation timevalue (ΔGOTV) with a global operation time threshold, wherein the globaloperation time value (ΔGOTV) comprises a difference of a current globaloperation time value (CGOTV) and a reset global operation time value(RGOTV).

According to at least one example of the method, the absence of the PTUshift between the 2WD mode and the AWD mode for the threshold amount ofvehicle operation comprises: incrementing a counter in response to anyof the following: (a) determining that a requested driver mode is the2WD mode, determining that the PTU is in the AWD mode, andunsuccessfully attempting to move the PTU to the 2WD mode; (b)determining that the requested driver mode is the AWD mode, determiningthat the PTU is in the 2WD mode, and unsuccessfully attempting to movethe PTU to the AWD mode; (c) determining that the requested driver modeis the 2WD mode and determining that the PTU is already in the 2WD mode;or (d) determining that the requested driver mode is the AWD mode anddetermining that the PTU is already in the AWD mode.

According to at least one example of the method, the PTU is coupled to amanual transmission.

According to at least one example, a computer is disclosed thatcomprises a processor and memory storing instructions executable by theprocessor, wherein the instructions comprises any combination of theexamples above.

According to another example, a system for performing a power transferunit (PTU) maintenance task is described that comprises: a processor;and memory storing instructions executable by the processor, theinstructions comprising, to: determine an absence of a PTU shift for adistance threshold or a global operation time threshold; then, determinethat a vehicle ignition state is not in a RUN state; and then, executethe task.

According to at least one example of the system, the instructionsfurther comprise: prior to determining that the ignition state is notthe RUN state, determine a PTU shift between a two-wheel drive (2WD)mode and an all-wheel drive (AWD) mode; and then, reset at least onecounter associated with the distance threshold or the global operationtime threshold.

According to at least one example of the system, the task comprisesmoving one or more components of an actuator of the PTU between aconnected and disconnected state.

According to at least one example of the system, the instructionsfurther comprise, to: while the ignition state is the RUN state,determine a communication error or a read-memory error; then, determinethat the ignition state is not in the RUN state and execute the task.

According to at least one example of the system, the instructionsfurther comprise, to: execute the task during an extended_ON mode whichprovides electrical power for the processor when the ignition state isan OFF state.

According to at least one example of the system, the absence of the PTUshift for the distance threshold or the global operation time thresholdfurther comprises an instruction, to: increment a counter in response toany of the following: (a) determining that a requested driver mode is atwo-wheel drive (2WD) mode, determining that the PTU is in an all-wheeldrive (AWD) mode, and unsuccessfully attempting to move the PTU to the2WD mode; (b) determining that the requested driver mode is the AWDmode, determining that the PTU is in the 2WD mode, and unsuccessfullyattempting to move the PTU to the AWD mode; (c) determining that therequested driver mode is the 2WD mode and determining that the PTU isalready in the 2WD mode; or (d) determining that the requested drivermode is the AWD mode and determining that the PTU is already in the AWDmode.

According to at least one example of the system, the system furthercomprises: the PTU and a computer that comprises the processor andmemory.

According to at least one example, a computer program product isdisclosed that comprises a computer readable medium storing instructionsexecutable by a computer processor, wherein the instructions comprisesany combination of the method or system examples above.

Now turning to the figures, wherein like numerals indicate like partsthroughout the several views, there is shown a powertrain system 10 fora vehicle 12 that includes an engine 14, a gearing system 16 (e.g., suchas a transaxle), and a driveline system 20 which may comprise a computer22 and a power take-off unit (PTU) 24 (e.g., also called a powertransfer unit) coupled to the gearing system 16 and also to a secondarydrive unit (SDU) 26 via a drive shaft 28. The vehicle 12 further maycomprise a primary axle 34 driven by the engine 14 and gearing system 16and a secondary axle 36 selectively driven by the engine 14 and gearingsystem 16 via the driveline system 20. The description below and theaccompanying illustrations show primary axle 34 as a front drive axle ofvehicle 12 and secondary axle 36 as a drive rear axle thereof; however,this is not required (for instance, in other examples, the secondaryaxle 36 could be located forward of primary axle 34).

According to at least one example, the computer 22 of the drivelinesystem 20 is programmed to execute a set of instructions for performingonboard maintenance for the PTU 24 when an ignition state of engine 14is not in a RUN state (e.g., sometimes referred to as an ON state) andnot in a START state (e.g., used to trigger a start of engine 14). Forexample, the vehicle 12 may have a plurality of ignition states such asan OFF state (e.g., sometimes referred to as a LOCK state), an accessory(ACC) state, the START state, and the RUN state. Some vehicles may beequipped with additional ignition states (e.g., such as a PREHEAT statefor warming the engine 14), and these additional states also arecontemplated herein. According to at least one example, in the RUNstate, the PTU 24 may be actuated to facilitate vehicle operation in atwo-wheel drive mode or an all-wheel drive mode, wherein, in the OFF,ACC, PREHEAT, or START states, the PTU 24 typically is not shiftedbetween two-wheel and all-wheel drive modes. In at least one example,computer 22 may be programmed to determine a maintenance event (e.g.,based on one or more maintenance triggers), determine that the vehicleignition state has changed from RUN to OFF or ACC, and keep computer 22awake (e.g., in an extended_ON mode) so that a maintenance task for thePTU 24 may be executed prior to computer 22 entering an OFF or ACCstate. As used herein, the computer 22 determining a PTU maintenanceevent means that the computer 22 has determined at least one conditionindicating a PTU maintenance task should be executed (e.g., as discussedbelow, conditions may include determining that a counter value is largerthan a threshold, determining a communication error between drivelinecomponents, determining a read-memory error of computer 22, and thelike, just to name a few). As used herein, the computer 22 executing amaintenance task means that the computer 22 controls movement of PTUcomponents (e.g., such as an actuator and/or its sub-components, asdescribed below) within a sealed housing (not shown) for the purpose ofdistributing lubricant around and/or between such moving PTU components.Lubricant may comprise any suitable fluid for reducing friction betweenand/or cooling components which move into and out of contact with oneanother (e.g., a non-solvent transmission fluid).

Exemplary vehicle 12 and powertrain system 10 are described below.Thereafter, an exemplary computer process will be described—e.g.,illustrating executable instructions of computer 22 used to control thedriveline system 20.

In FIG. 1, vehicle 12 is shown as a passenger car; however, vehicle 12could also be a truck, sports utility vehicle (SUV), recreationalvehicle, bus, or any other suitable vehicle that comprises thepowertrain system 10. The vehicle 12 may be comprise wheels, continuoustrack, a combination thereof, or the like. The powertrain system 10 maybe carried by a frame, a unibody, etc. of the vehicle 12—e.g., inaccordance with techniques known in the art.

The primary and secondary axles 34, 36 of vehicle 12 may be coupled towheels 42, 44, 46, 48. More particularly, primary axle 34 may comprisehalfshafts 34 a, 34 b which are coupled to wheels 42, 44, respectively.And secondary axle 36 may comprise halfshafts 36 a, 36 b which arecoupled to wheels 46, 48, respectively. In this manner, wheels 42-48 mayrotate independent of one another and/or at different rates of speed.

In at least the illustrated example, the primary axle 34 is locatedforward of secondary axle 36, and primary axle 34 is coupled directly togearing system 16. Correspondingly, secondary axle 36 is coupledindirectly to gearing system 16 via PTU 24, drive shaft 28, and SDU 26(e.g., which may include a clutch 40). Again, this arrangement is merelyan example; other arrangements exist including those wherein thesecondary axle is located vehicle forwardly of the primary axle, whereinthe engine 14 and/or gearing system 16 are located vehicle centricallyor vehicle rearwardly, wherein vehicle 12 comprises three or more axles,wherein two or more secondary axles are used, wherein a combination ofthese arrangements is used, etc. Thus, while the SDU 26 may be a reardrive unit in the illustrations; this is not required (e.g., it could bea front drive unit in other examples).

Powertrain system 10 may be any power delivery system used to propel thevehicle 12 that includes the engine 14 and gearing system 16. As will bedescribed more below, system 10 may comprise a vehicle havingfront-wheel drive (FWD) or rear-wheel drive (RWD) capability, plusselective all-wheel drive capability. Again, for purposes ofillustration only, FIG. 1 illustrates vehicle 12 selectively operable ina two-wheel drive (2WD) mode and an all-wheel drive (AWD) mode (i.e.,when the SDU 26 is engaged). As used herein, the phrase all-wheel drive(AWD) mode is used broadly to include various types of all-wheel driveimplementations; thus, for example the phrase all-wheel drive (AWD) modeincludes four-wheel drive (4WD) mode and the like.

Engine 14 of powertrain system 10 may be any suitable motor orcombination of motors which deliver rotational kinetic energy to thegearing system 16—which energy ultimately is deliverable to the wheels42-48 via mechanical linkages. Non-limiting engine examples includecombustion engines, electric engines, hybrid-electric engines, etc.,just to name a few.

Gearing system 16 of powertrain system 10 may comprise a transmissionmechanically coupled to engine 14 which may be used to create differentgear ratios allowing different trade-offs between torque delivery androtational speed. The gearing system 16 may comprise a so-calledtransaxle; e.g., a transaxle may comprise multiple transmission gears(not shown) and a differential (not shown) coupled to each of halfshafts34 a, 34 b. Of course, other types of transmission systems may be usedinstead. According to one non-limiting example, the gearing system 16comprises a manual transmission; as used herein, a manual transmissioncomprises a clutch which may be engaged and disengaged via vehicle user(e.g., driver) control to regulate torque transfer from the engine 14 tothe vehicle wheel(s), track, etc. via the driveline system 20.

Driveline system 20 may form a portion of powertrain system 10—e.g.,being coupled to the gearing system 16. According to one example,driveline system 20 may comprise the computer 22, power take-off unit(PTU) 24, drive shaft 28, and secondary drive unit (SDU) 26, asdiscussed above. According to the illustrated example, engagementbetween gearing system 16 and PTU 24 may be used to change torquedelivery to each of wheels 42, 44, 46, 48—e.g., changing from the 2WDmode to the AWD mode. Similarly, disengagement of the PTU 24 from thegearing system 16 may change the vehicle 12 from the AWD mode to the 2WDmode. Each driveline system component will be described in turn.

Turning now to FIG. 2, an electrical architecture diagram of vehicle 12is shown that includes computer 22. Computer 22 comprises a singlecomputer or multiple computers (e.g., which may or may not be sharedwith other vehicle systems and/or subsystems). Computer 22 isprogrammed—at least in part—to monitor sensor data from and/or controlaspects of the PTU 24 and/or to monitor sensor data from and/or controlaspects of the SDU 26. According to at least one example, computer 22and SDU 26 share a common housing and collectively comprise a secondarydrive module (SDM) 50 (shown in phantom); however, this is not required.In another example, hardware of computer 22 and PTU 24 may share acommon housing. Or for example, hardware of computer 22 may bepartitioned from SDU 26 and PTU 24 and/or combined with other vehiclecomponents. In addition, in other examples, the computer 22 is locatedelsewhere in vehicle 12—e.g., not adjacent to or within the same moduleas SDU 26. Other arrangements are also possible.

Computer 22 comprises a processor 52 and memory 54—and in some examplesalso may comprise a PTU control circuit 56 and a SDU control circuit 58.Processor 52 can be any type of device capable of processing electronicinstructions; non-limiting examples include a microprocessor, amicrocontroller or controller, an application specific integratedcircuit (ASIC), etc.—just to name a few. Processor 52 may be coupledelectronically to memory 54 and circuits 56, 58. In general, computer 22may be programmed to send data to and/or receive data from circuits 56,58, as well as to execute digital instructions, which may be stored inmemory 54, which enable the computer 22, among other things, todetermine a maintenance event and execute instructions to perform a PTUmaintenance task. Illustrative programmable instructions stored inmemory 54 and executable by processor 52 will be discussed in greaterdetail below.

Memory 54 may include any non-transitory computer usable or readablemedium, which may include one or more storage devices or articles.Exemplary non-transitory computer usable storage devices includeconventional hard disk, solid-state memory, random-access memory (RAM),read-only memory (ROM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), as well asany other volatile or non-volatile media. According to at least oneexample, memory 54 comprises EEPROM. And in at least one example, EEPROMmemory 54 is used to store counter data and flag data associated withthe maintenance event; thus, such data may be recalled from memory 54when computer 22 boots up and thus may be used by processor 52 todetermine whether and when to trigger a maintenance event.

Non-volatile media include, for example, optical or magnetic disks andother persistent memory, and volatile media, for example, also mayinclude dynamic random-access memory (DRAM). These storage devices arenon-limiting examples; e.g., other forms of computer-readable mediaexist and include magnetic media, compact disc ROM (CD-ROMs), digitalvideo disc (DVDs), other optical media, any suitable memory chip orcartridge, or any other medium from which a computer can read. Asdiscussed above, memory 54 may store one or more computer programproducts which may be embodied as software, firmware, or otherprogramming instructions executable by the processor 52.

PTU control circuit 56 may comprise any suitable electronics forcontrolling an actuator 62 of PTU 24 (discussed below), any suitableelectronics for sensing voltage, current, temperature, or otherconditions at the PTU 24, or a combination thereof. Similarly, the SDUcontrol circuit 58 comprise any suitable electronics for controlling anactuator 64 (shown in FIGS. 1, 2 and discussed below) of SDU 26, anysuitable electronics for sensing voltage, current, temperature, or otherconditions at the SDU 26, or a combination thereof. Accordingly,computer processor 52 may execute instructions enabling it to controlone or both of circuits 56, 58 to carry out one or more of the processesdescribed herein.

Computer 22 may be coupled to a wired or wireless communication networkconnection 55 which permits communication between computer 22 and otherelectronic devices. Network connection 55 may include one or more of acontroller area network (CAN) bus, Ethernet, Local Interconnect Network(LIN), a fiber optic connection, or the like—just to name a fewnon-limiting examples. In some examples, connection 55 comprises one ormore discrete connections, a bus connection, or a combination thereof.According to at least one example, network connection 55 comprises a CANbus having CAN bus signals which are used by computer 22 and otherdevices for intra-vehicle communication.

Computer 22 may be programmed to determine communication errors receivedvia or at connection 55. Non-limiting examples of communication errorsinclude malfunctions of or error messages over the network connection55. For example, computer 22 may be programmed with instructions todetect a CAN bus error based on detecting a connection failure (e.g.computer 22 being unable to communicate with another networked device onthe bus), a node failure (e.g., receiving returned values indicating anerror), a combination thereof, or the like. Further, computer 22 may beprogrammed with instructions to detect pre-configured error messages(e.g., also referred to herein as communication errors) on the bus orother type of network connection. Other examples of communication errorsmay be determined by computer 22 as well.

As shown in FIGS. 1, 1A and 2, PTU 24 comprises any suitable hardwarecomponent(s) that receive input torque from gearing system 16 andprovide output torque to an auxiliary hardware device. In theillustrated example, the PTU 24 provides output torque to at least theSDU 26 via drive shaft 28. For purposes of illustration only (and notintending to be limiting), PTU 24 may comprise an input shaft 70 that isconfigured to receive a torque input from gearing system 16 and at leastone output shaft 72 which may deliver torque output to the SDU 26 viadrive shaft 28 when actuator 62 is in an engaged state. As will bedescribed more below, the actuator 62 may be moved between the engagedstate and a disengaged state—e.g., controlled by PTU control circuit 56(of computer 22). Thus, in the engaged state, torque may be transferredfrom the gearing system 16, through the input and output shafts 70, 72,through the drive shaft 28, through the SDU 26, and to the rear wheels46, 48.

Actuator 62 may comprise any suitable electronically actuated mechanicallinkage between the PTU 24 and the drive shaft 28. For example, theactuator 62 may comprise a switch 73 (e.g., such as a solenoid) which,when selectively actuated by the PTU control circuit 56, mechanicallycouples the PTU 24 and drive shaft 28 (into the engaged state).Similarly, the PTU 24 and drive shaft 28 may be de-coupled by the PTUcontrol circuit 56 controlling switch 73 (e.g., thereby disengaging thedrive shaft 28 and SDU 26).

FIG. 1A illustrates a non-limiting example of actuator 62 (in adisengaged state) that further includes a driving member 74 (which maybe mechanically coupled to input shaft 70), a driven member 76 (whichmay be mechanically coupled to output shaft 72), and an engagingmechanism 78 that moves the driving member 74 to engage or disengage thedriven member 76. According to at least one example, the driving member74 comprises a dog clutch (exemplified in the illustrations as anannulus having one or more radially-inwardly-extending teeth 80), thedriven member 76 comprises a gear (exemplified in the illustrations asan annulus having one or more radially-outwardly-extending teeth 82 thatare sized and shaped to correspondingly engage teeth 80), and theengaging mechanism 78 comprise a rail 84 coupled to a shifter fork 86.For example, fork 86 may be fixed to both an outer surface 88 of thedriving member 74 at one end and the rail 84 (at an opposite end).According to an exemplary operation, the control circuit 56 of computer22—via network connection 55—axially may move rail 84 in a firstdirection thereby moving the dog clutch 74 to a disengaged state (e.g.,as shown in FIG. 1A), and the control circuit 56 axially may move rail84 in a second, opposite direction until the teeth 80 engage teeth 82,thereby moving the dog clutch 74 to an engaged state. In this latterinstance, torque at input shaft 70 causes torque to be delivered atoutput shaft 72 (e.g., thus, driving SDU 26 via drive shaft 28) (e.g.,in other words, an AWD mode).

One example of a bilateral actuator is shown and described above.However, unilateral and other bilateral actuator examples also exist. Inthese examples, one or more different components may be used; thus, thedriving member 74, the driven member 76, and the engaging mechanism 78are merely examples and are not required in all implementations.

Furthermore, the switch 73 is optional as well. For example, in manualtransmission implementations, switch 73 may be omitted permitting avehicle driver to manually operate the engaging mechanism 78 (e.g.,moving to the first or second positions).

Returning to FIG. 1, drive shaft 28 may comprise any suitable mechanicallinkage between the output shaft 72 of PTU 24 and SDU 26 whichfacilitates the delivery of torque to the SDU 26. Drive shaft 28 maycomprise a rigid, elongated rod or member, coupling components such asuniversal joints, etc. (for coupling to PTU 24 and the SDU 26), and thelike, all of which will be appreciated by those skilled in the art.

SDU 26 may comprise any suitable mechanical component at secondary axle36 which is configured to receive torque from the drive shaft 28 (viaclutch 40) and deliver said torque to the wheels 46, 48. SDU 26 maycomprise a differential—e.g., so that halfshafts 36 a, 36 b (which arecoupled thereto) permit wheels 46, 48 to rotate at different rates ofspeed and/or be delivered different amounts of torque. As discussedabove, SDU 26 could be a rear drive unit or be located instead at afront axle (e.g., as a front drive unit; e.g., in rear-wheel drivevehicles).

SDU 26 also may comprise clutch 40 and actuator 64. Clutch 40 maycomprise any suitable mechanical component interposed between the SDU 26and either wheel 46, 48 which may be moved between an engaged state anda disengaged state by actuator 64. According to one example, clutch 40may comprise a set of braking plates and a set of interstitially-locatedfriction plates, as well as other components and features whichfacilitate movement of at least one set of the plates toward theother—e.g., so that the clutch moves between an engaged state and adisengaged state. Other aspects of a clutch, as well as assembly andoperation techniques, are known in the art. Thus, when clutch 40 is inthe engaged state, torque transferred from the PTU 24 and drive shaft 28to the SDU 26 is then transferred to the wheels 46, 48. And no torque istransferred to wheels 46, 48 when the clutch 40 is in the disengagedstate.

The clutch 40 may move between the engaged and disengaged states inresponse to actuation of actuator 64, and actuator 64 may be controlledby computer 22 (e.g., via SDU control circuit 58). According to at leastone example, actuator 64 may be similar or identical to actuator 62;therefore, it will not be described in greater detail here.

FIG. 2 illustrates that vehicle 12 also may comprise a human-machineinterface (HMI) module 90 and an ignition module 92, each of which maybe coupled communicatively to network connection 55. The HMI module 90may include any suitable input and/or output devices such as switches,knobs, one or more levers, controls, etc.—e.g., on a vehicle instrumentpanel, steering wheel, floorboard, console, etc. of vehicle 12—which maybe coupled communicatively to computer 22. In one non-limiting example,HMI module 90 may comprise an interactive touch screen or display whichprovides powertrain information (e.g., including text, images, etc.) tothe vehicle driver, and a switch or knob on the HMI module 90 permitsthe driver to switch between the 2WD mode and the AWD mode. The HMImodule 90 further may be used to notify the driver that a PTUmaintenance task is being executed. At least one example of HMI module90 comprises a mechanical linkage (e.g., a manual lever to actuate a 2WDmode or an AWD mode); in this instance, the HMI module 90 may not becoupled to network connection 55.

The ignition module 92 may comprise an ignition switch 94 coupled toengine 14 and an electronic control unit (ECU) 96 that, among otherthings, monitors a vehicle ignition state of vehicle 12. Switch 94 maybe moved to a plurality of positions that correspond with the differentignition states (discussed above). According to one non-limitingexample, the switch 94 may be moved to any one of five positions whichcorrespond with a RUN state, an ACC state, a PREHEAT state, a STARTstate, or an OFF state. In the RUN state, the engine 14 may be poweredregardless of whether the engine 14 is engaged to the gearing system 16.In the ACC state, one or more vehicle accessories (e.g., such as the HMImodule 90) may be operable, even though the engine 14 may be OFF. In thePREHEAT state, the engine 14 may be unpowered; however, one or moreheating elements (not shown) may be actuated to warm selected orpredetermined components, fluids, etc. In the START state, the switch 94may provide an electrical connection to enable the engine 14 totransition from the OFF state to the RUN state (e.g., providing power toelectric motors in electric vehicle implementations, providing currentto spark plugs in combustion engine implementations, or the like). Andin the OFF state, the engine 14 may be unpowered or OFF. According toone example, when the ignition state is triggered to OFF, a substantialquantity of vehicle electrical systems power to OFF; some may revert toa LOW-POWER state—e.g., thereby conserving battery power for later startand/or operation. According to an example described in the processbelow, the computer 22 may determine a maintenance event during the RUNstate and later—when the ignition state is not in the RUN state or theSTART state—perform a maintenance task based on the earlierdetermination.

ECU 96 of ignition module 92 may comprise a processor, memory,electronic circuit components, or a combination thereof. According to atleast one example, at least some of the hardware of ECU 96 may besimilar or identical to the processor and memory of computer 22;therefore, the components of ECU 96 will not be described in detailhere. Of course, instructions executable by the ECU 96 may differ fromthose stored in computer 22. For example, ECU 96 may determine and/orcontrol the position of switch 94, communicate via network connection55, and the like. Ignition control techniques are generally known andwill not be described in detail herein. Further, ECU 96 is optional;e.g., in at least one example, the ignition module 92 includes theswitch 94 without ECU 96 (e.g., electrical signals via discrete networkconnections 55 may be coupled to computer 22).

Turning now to FIGS. 3-6, a process 300 is shown for determining amaintenance event at the PTU 24 and then performing a correspondingmaintenance task for the PTU 24. The process 300 is illustrated as aflow diagram of blocks comprising instructions executable by processor52 of computer 22. According to one example, the process may begin withblock 320 which includes computer 22 receiving an indication that anignition state of vehicle 12 is the RUN state. According to at least oneexample, the computer 22 receives this indication in the form of amessage from the ignition module 92—e.g., received via the networkconnection 55.

Block 330 follows block 320. In block 330, computer 22 may check orotherwise determine whether any communication errors exist or whether aread-memory errors exist. As discussed above, communication errors maycomprise error message(s) received over connection 55, connectionfailure indication(s) (or connection failure determinations), nodefailure indication(s) (or node failure determinations), or the like.Read-memory errors may be any error associated with, derived from, orindicated by memory 54. According to one example, a read-memory errorcomprises an inability of processor 52 to read data stored in memory 54(e.g., during an ignition cycle or while during an extended_ON mode(discussed below) that occurs when the ignition state may be OFF, ACC,or PREHEAT). According to another example, a read-memory error comprisesa memory error message (e.g., that all or a portion of the memory 54 iscorrupted). According to another example, a read-memory error comprisesprocessor 52 reading data from the memory 54, however, determining thatone or more data values (e.g., counter data or flag data) isout-of-range—i.e., is outside of predetermined upper and/or lower limitvalues. These are merely examples; other types of read-memory errors mayexist. When at least one of a communication error or a read-memory erroris determined in block 330, computer 22 may determine a maintenanceevent at the PTU 24 and thus determine to perform a maintenance task (asdescribed more below). More particularly, when at least one of acommunication error or a read-memory error is determined in block 330,process 300 may proceed to block 605. And when neither of acommunication error nor a read-memory error is determined in block 330,process 300 may proceed to block 335.

In block 335, computer 22 may determine that a user (e.g., a driver) ofvehicle 12 requests a driving mode (e.g., a 2WD mode, an AWD mode,etc.). Such a request may include a message or indication from HMImodule 90 or the like. Further, the request may be explicit orimplicit—e.g., an explicit request may comprise the driver positivelyactuating or otherwise actively selecting one of the levers, knobs,controls, etc. on HMI module 90, whereas an implicit request maycomprise no positive actuation or selection of any portion of the HMImodule 90 implying that the driver desires to maintain the what he orshe believes to be the current driving mode. Thus, in block 335, whencomputer 22 determines that the 2WD mode is requested, the process 300may proceed to block 340, and when, in block 335, computer 22 determinesthat the AWD mode is requested, the process 300 may proceed to block360.

In block 340, computer 22 determines whether the PTU 24 is disengagedfrom the SDU 26. For example, processor 52 may receive an indicationfrom PTU control circuit 56, wherein circuit 56 determines the positionof the actuator 62 (e.g., via one or more sensors (not shown) atactuator 62). According to one example, computer 22 determines whetherthe engaging mechanism 78 (e.g., rail 84) is in the first position orthe second position. If the computer 22 determines that the PTU 24 isalready disengaged (e.g., rail 84 is in the first position), thenprocess 300 proceeds to block 345. And if the computer 22 determinesthat the PTU 24 is engaged (e.g., the PTU 24 is in the AWD mode and rail84 is in the second position), then process 300 proceeds to block 350.

In block 345, one or more counters of computer 22 may be incremented.One example of block 345 is shown in FIG. 4, wherein block 345 isillustrated as a subroutine or subset of instructions. Accordingly, asdescribed more below, any of blocks 340, 355, and 360 may flow to block345, and block 600 may follow any instructions executed in block 345.

Accordingly, following block 340 (for example) computer 22 mayreceive—via network connection 55—a current odometer value (COV) (e.g.,a current mileage value in block 450) and a current global operationtime value (CGOTV) (e.g., a time parameter in block 455). In block 460which follows blocks 450 and 455, computer 22 may determine whether thecurrent odometer value (COV) is greater than a last-received odometervalue (LOV). Following each time process 300 executes block 345, thelast-received odometer value (LOV) may be set equal to the currentodometer value (COV) and thereafter stored in memory 54. In block 460,when the current odometer value (COV) is greater than the last-receivedodometer value (LOV), then the process 300 proceeds to block 470, andwhen it is not greater than the last-received odometer value (LOV), thenit proceeds to block 465.

In block 470, computer 22 may determine a distance counter value (e.g.,a change in odometer value (ΔOV)), wherein ΔOV equals the currentodometer value (COV) less a reset odometer value (ROV). See Equation(1).

ΔOV=COV−ROV   Equation (1)

The reset odometer value (ROV) may be reset each time distance andglobal operation time counters are reset, as described below. In block475, counter data such as the last-received odometer value (LOV), thedistance counter value (ΔOV), and reset odometer value (ROV) may bestored in non-volatile memory 54 (e.g., and available to computer 22after the current ignition cycle ends). As described more below, thedistance counter value (ΔOV) may be compared with a threshold at timesduring process 300; and when the distance counter value (ΔOV) is largerthan the threshold, then the computer 22 may determine to perform thePTU maintenance event to facilitate adequate moving of the PTU actuator62 between an engaged (connected) and disengaged (disconnected) state.As described below, according to one example, moving the actuator 62 maycomprise cycling between the engaged and disengaged state one or moretimes.

The global operation time counter may operate similarly to the distancecounter except that it may monitor global operation time data and storecounter data associated therewith. As used herein, a global operationtime data is a collective measure of time (from a time of vehiclemanufacture) measuring when the vehicle ignition state is in the RUNstate, the ACC state, and/or the PREHEAT state. Accordingly, the globaloperation time value (CGOTV) received in block 455 is a current value ofthat collective measure of time. For example, in block 465, computer 22may determine whether the current global operation time value (CGOTV) isgreater than a last-received global operation time value (LGOTV).Similar to the LOV instruction described above, following each timeprocess 300 executes block 345, the last-received global operation timevalue (LGOTV) may be set equal to the current global operation timevalue (CGOTV) and thereafter stored in memory 54. In block 465, when thecurrent global operation time value (CGOTV) is greater than thelast-received global operation time value (LGOTV), then the process 300proceeds to block 480, and when it is not greater than the last-receivedglobal operation time value (LGOTV), then it proceeds to block 600.

In block 480, computer 22 may determine a global operation time value(e.g., a change in global operation time value (ΔGOTV)), wherein ΔGOTVequals the current global operation time value (CGOTV) less a resetglobal operation time value (RGOTV). The reset global operation timevalue (RGOTV) may be a time indicating when the last counter resetoccurred. See Equation (2).

ΔGOTV=CGOTV−RGOTV   Equation (2)

The reset global operation time value (RGOTV) may be reset each time thedistance and global operation time counters are reset, as describedbelow. In block 485, counter data such as the last-received globaloperation time value (LGOTV), the global operation time value (ΔGOTV),and reset global operation time value (RGOTV) may be stored innon-volatile memory 54 (e.g., and available to computer 22 after thecurrent ignition cycle ends). As described more below, the globaloperation time value (ΔGOTV) may be compared with a threshold at timesduring process 300; and when the global operation time value (ΔGOTV) islarger than the respective threshold, then the computer 22 may determineto perform PTU maintenance event to facilitate adequate moving of thePTU actuator 62 between an engaged (connected) and disengaged(disconnected) state.

Block 600—which follows block 345 (or more specifically, either ofblocks 465 or 485)—will be described below. Returning to FIG. 3, recallthat block 350 may follow block 340 (described above)—or may followblock 360 (described below). In block 350, computer 22—e.g., via controlcircuit 56—may attempt to move the PTU 24 to the requested mode. Forexample, when the request (in block 335) is for 2WD mode, then in block350, the computer 22 may control the actuator 62 to disengage PTU 24.Similarly, when the request (in block 335) is for AWD mode, then inblock 350, the computer 22 may control the actuator 62 to engage the PTU(e.g., enter AWD mode). Continuing with the present flow path (e.g.,block 335 to block 340 to block 350), the computer 22 may attempt todisengage the PTU 24 from the SDU 26 (enter 2WD mode).

In block 355 which follows block 350, computer 22 may determine whethera successful PTU shift occurred. As used herein, a successful PTU shiftmay comprise moving the actuator 62 from the disengaged state to theengaged state, or vice-versa. In at least one example, a successful PTUshift further may comprise doing so within a predetermined interval oftime—e.g., a PTU shift within a predetermined response time can improvethe driver experience. In at least one example, an unsuccessful shiftmay comprise displacement of the actuator 62 less than a thresholdamount; in the example shown in FIG. 1A, an unsuccessful shift maycomprise moving the driving member 74 only partially between the firstand second positions or the like. Another example of an unsuccessfulshift may include moving the driving member 74 between the first andsecond positions; however, the predetermined interval being greater thana predetermined threshold. When the computer 22 determines a successfulshift in block 355, then process 300 proceeds to block 500. And when thecomputer 22 determines an unsuccessful shift in block 355, then process300 proceeds to block 345 (which has already been described above).

Turning now to block 360, recall process 300 may proceed to block 360when the requested mode (block 335) is the AWD mode. Block 360 may besimilar to block 340; therefore, it will not be described in detailagain. When computer 22 determines that the PTU 24 is engaged already(e.g., rail 84 is in the second position), then process 300 may proceedto block 345 (e.g., and may increment the counter(s)). And when computer22 determines that the PTU 24 is disengaged (e.g., the PTU 24 is in the2WD mode; e.g., rail 84 is in the first position), then process 300 mayproceed to block 350 (also previously described).

Turning now to FIG. 5, according to at least one implementation of block500, computer 22 may reset the distance counter and the global operationtime counter. To reset the distance counter, computer 22 may receive acurrent odometer value (COV) and set the reset odometer value (ROV)equal to this current odometer value (COV). In this manner, the distancecounter value (ΔOV) is reset effectively to zero (e.g., see Equation(1)).

Resetting the global operation time counter may be carried out bysetting the reset global operation time value (RGOTV) to the currentglobal operation time value (CGOTV). In this manner, the globaloperation time value (ΔGOTV) is reset effectively to zero as well (e.g.,see Equation (2)).

Block 500 further may comprise setting a maintenance event flag to aFALSE value. As explained more below, when the value of this flag isTRUE, then computer 22 may determine a maintenance event for the PTU24—e.g., and perform the maintenance event when the ignition state isother than RUN or START. It should be appreciated that in some instancesduring a current ignition cycle, the flag could be set to TRUE at onepoint, the process 300 could loop back and repeat at least some ofblocks 330-360 thereafter changing the PTU 24 from the 2WD mode to theAWD mode (or vice-versa), and the flag could be set back to FALSE (e.g.,without performing the maintenance event). Thus, according to one aspectof process 300, computer 22 determines instances when the PTU 24 doesnot move between 2WD and AWD modes for a predetermined measure ofmileage or global operation time, and then attempts to move thecomponents of the PTU actuator 62 by performing a maintenance event, asdiscussed more below.

It should be appreciated that a flag is merely one example and is notintended to be limiting. For example, the flag may be implemented as astate or condition storable in memory 54; or the flag may represent anelectrical switch (e.g., a transistor) position ON or OFF or a switchwithin processor 52. Other examples also exist. Following block 500, theprocess 300 may proceed to block 600.

In block 600 (FIG. 6), computer 22 determines whether the counter(s) aregreater than their respective thresholds. As discussed above, computer22 may compare the distance counter value (ΔOV) to a calibratablemileage threshold and/or the global operation time value (ΔGOTV) to acalibratable global operation time threshold. According to one example,if either of the values are greater than their respective thresholds,then process 300 proceeds to block 605, and if neither of the values aregreater than their respective thresholds, then process 300 proceeds toblock 640.

In block 605, the computer 22 determines the PTU maintenance event andaccordingly may set the maintenance event flag to a TRUE value. (Note:FIG. 6 illustrates that process 300 may flow to block 605 from block 330as well, as described above.)

In block 610 which follows, computer 22 may determine whether theignition state does not equal the RUN state and does not equal the STARTstate (e.g., alternatively, computer 22 could determine only whether thevehicle ignition state is not in the RUN state). When the vehicle 12 isoperating in either the RUN or START state, the process 300 may loopback to block 335 (e.g., determining again the driver requested PTUmode). However, when the ignition state is not the RUN state and is notthe START state—e.g., but instead one of the OFF state, the ACC state,or the PREHEAT state—then process 300 proceeds to block 615.

Typically, when the ignition state transitions from the RUN state to oneof the OFF, PREHEAT, or ACC states, computer 22 would receive anindication to shut-down vehicle electronics; e.g., if the engine is OFF,there is typically no shifting between 2WD and AWD modes. In block 615,computer 22 may set an operational mode to an extended_ON mode (e.g.,operates in a mode that overrides the typical vehicle electronicsshut-down). Thus, in this extended_ON mode, PTU 24 may have limitedfunctionality, and computer 22 may execute, among other things, the PTUmaintenance task. In at least one example, the computer 22 (e.g., whichmay be located in the SDU 26 or elsewhere) and the actuator 62 remain atleast partially powered.

In block 620 which follows, computer 22 may initiate the PTU maintenancetask. As discussed above, a PTU maintenance task includes moving theactuator components of the PTU 24 (e.g., components such as, but notlimited to, switch 73, rail 84, sifter fork 86, driving member 74, anddriven member 76 which have intermeshing teeth 80, 82, respectively)between an engaged (connected) and disengaged (disconnected) state.According to one non-limiting example, computer 22 may move the actuator62 from the first position to the second position (or vice-versa). Insome examples, this movement may be reciprocated a predeterminedquantity of times (e.g., for a bilateral actuator). In another example,movement of the actuator 62 in a single direction can adequately promotecomponent function (e.g., for a unilateral actuator). In anotherexample, computer 22 may command the maintenance task, and if the taskis not executed within a predetermined period of time (e.g., indicatingthat the PTU components are unlubricated, locked-up, or have too muchfriction), then the maintenance task may be repeated one or moretimes—e.g., attempting to complete the task within the predeterminedperiod of time.

Blocks 625-635 which follow block 620 may occur in any sequence or mayoccur at least partially concurrently. For example, in block 625,computer 22 may re-determine whether the ignition state still is not inthe RUN or START state. If for example the driver again restarts thevehicle 12 and places the engine 14 in the RUN state, then (as discussedbelow) it may be desirable to abort the maintenance task because thedriver may desire shift and/or use the functionality of the PTU 24. Whenthe ignition state does not equal either of RUN or START, then theprocess 300 may proceed to block 630, and when if the ignition state nowequals RUN or START, then the process 300 may proceed to block 530.

In block 630, computer 22 may determine whether the PTU 24 isexperiencing a failure mode. Non-limiting examples of failure modesinclude: electrical power-draw errors at the PTU 24, PTU positionerrors, or the like. For example, non-limiting examples of power-drawerrors include: a voltage level error (e.g., a voltage level, less thana predetermined value, greater than a predetermined value, or outside athreshold range); a current draw level error (e.g., a current draw lessthan a predetermined value, greater than a predetermined value, oroutside a threshold range); a voltage or current stability error (e.g.,a measurement of voltage or current for a period of time, wherein duringthe period, instantaneous values of the current or voltage varypositively or negatively more than a threshold amount); and the like.And for example, non-limiting examples of PTU position errors include: astate unknown error (e.g., an error indicating that a state of the PTUactuator 62 is unknown—i.e., it is unknown whether the PTU 24 is in anengaged state or a disengaged state); an actuator position error (e.g.,an error indicating that the actuator 62 is stuck between the engagedand disengaged states); an out-of-range error (e.g., an error that canbe derived from an electrical measurement of the output of actuator 62indicating that the actuator 62 is outside a threshold range of motion);and the like. These are merely examples; other failure modes exist aswell. When the PTU 24 is experiencing at least one failure mode, thenthe process 300 may proceed to block 530, and when PTU 24 is notexperiencing a failure mode, then it may proceed to block 635.

In block 635, computer 22 may determine whether the PTU maintenance taskis complete. When the maintenance task is complete, then the process 300may proceed to block 510, and when the task is not complete, thenprocess 300 may loop back to block 625 and continue to loop throughblocks 625-635.

FIG. 6 also illustrates that process 300 may include block 640 which mayfollow block 600 when computer 22 determines that the counter(s) did notexceed their respective threshold(s). In block 640, the computer 22 maydetermine that the ignition state of vehicle 12 is still the RUN state.When the ignition state still equals the RUN state, then the process 300may loop back to block 330 (e.g., and checks again for communicationand/or read-memory errors), and when the ignition state is somethingother than the RUN state, then process 300 may proceed to block 550,discussed below.

Returning to FIG. 5, process 300 also may include blocks 510, 530, 550,and 560. In block 510 (which may follow block 635 when the PTUmaintenance task is completed), computer 22 may reset the distancecounter and the global operation time counter, and computer 22 may setthe maintenance event flag to a FALSE value again. According to oneexample, block 510 may be identical to block 500; thus, it will not bedescribed again in detail. Following block 510, the process may proceedto block 550.

In block 550 (which may follow any one of blocks 510, 530, or 640),computer 22 may store counter data (e.g., LOV, ΔOV, ROV, LGOTV, ΔGOTV,RGOTV, etc.) in PTU memory 54 so that they may be used later when thePTU computer 22 is rebooted (e.g., at a subsequent ignition cycle).According to one example, counter data is stored in EEPROM (or othersuitable non-volatile devices of memory 54), and flag data is stored inRAM (or other suitable volatile devices of memory 54).

In block 560 which may follow block 550, the operational mode ofcomputer 22 may change to a power-down mode. In one example, this may betriggered by the ignition cycle changing to OFF—e.g., vehicle 12 may beconfigured to command vehicle control modules and electronics to shutdown when the ignition cycle is OFF (or transitions to OFF) to conserveenergy. In other examples, computer 22 executes an instruction to enterthe power-down mode only after storing data in block 550 (and/or aftercompleting the PTU maintenance task in the extended_ON mode, discussedabove). Accordingly, computer 22 powers down and the process 300 mayend.

Block 530 (e.g., which may proceed from either of blocks 625 or 630) maycomprise computer 22 aborting the PTU maintenance task. For example, asdescribed above, when the maintenance task is interrupted beforecompletion, computer 22 may cease operation of the PTU maintenance taskand save the counter data in memory 54 in block 550 (which follows block530) and then power down (block 560). In this example, the counter datais not reset—e.g., so that upon the next ignition cycle, afterevaluating the counter data, flag will be set to the TRUE value and thecomputer 22 will identify that the PTU maintenance event still needs tobe completed.

Thus, process 300 may be used to trigger execution of a PTU maintenancetask when: (a) the computer 22 determines a communication error (e.g.,the computer 22 may be unable to identify which mode the PTU 24 isin—e.g., as the actuator 62 may be unable to communicate with thecomputer 22); (b) the computer 22 determines a read-memory error (e.g.,potentially suggesting that the counter and/or flag data may be invalid;and/or (c) the computer 22 determines that PTU 24 has not shifted ormoved between 2WD and AWD for a predetermined amount of global operationtime threshold or distance threshold (e.g., miles-driven threshold).Thus, when any one of these determinations is made, then a PTUmaintenance task may be executed when the PTU 24 is not being used(e.g., when the engine 14 is not in the RUN state).

If the PTU 24 is shifted between 2WD and AWD modes before the distancecounter reaches a threshold and/or the global operation time counterreaches its threshold, then no PTU maintenance task may be executed.

According to one example (of block 330 proceeding to block 605), even ifthe communication or read-memory error is resolved during the sameignition cycle, the flag having been set to TRUE (in block 605) mayremain TRUE—e.g., until the PTU 24 is actuated successfully.

Thus, there has been described a powertrain system for a vehicle. Thesystem includes a driveline system that can include a power-take offunit (PTU) and a computer. The computer may be programmed withinstructions that enable it to determine a PTU maintenance event andperform a PTU maintenance task. According to one example, the computermay determine the PTU maintenance event by determining at least one ofthe following: a communication error, a read-memory error, or an absenceof a PTU shift between a two-wheel drive (2WD) mode and an all-wheeldrive (AWD) mode for a threshold amount of time or distance. Havingdetermined the event, provided these conditions have not changed in theinterim, the computer may determine to execute the PTU maintenance taskbased on: the PTU maintenance event determination and a determinationthat a vehicle ignition station is not in a RUN state.

In general, the computing systems and/or devices described may employany of a number of computer operating systems, including, but by nomeans limited to, versions and/or varieties of the Windows EmbeddedAutomotive operating system, the Microsoft Windows operating system, theUnix operating system, the AIX UNIX operating system, the Linuxoperating system, the Mac OSX and iOS operating systems, or the like.Examples of computing devices include, without limitation, an on-boardvehicle computer or some other computing system and/or device on vehicle12.

Computing devices generally include computer-executable instructions,where the instructions may be executable by one or more computingdevices such as those listed above. Computer-executable instructions maybe compiled or interpreted from computer programs created using avariety of programming languages and/or technologies, including, withoutlimitation, and either alone or in combination, Java™, C, C++, VisualBasic, Java Script, Perl, etc. Some of these applications may becompiled and executed on a virtual machine, such as the Java VirtualMachine, the Dalvik virtual machine, or the like. In general, aprocessor (e.g., a microprocessor) receives instructions, e.g., from amemory, a computer-readable medium, etc., and executes theseinstructions, thereby performing one or more processes, including one ormore of the processes described herein. Such instructions and other datamay be stored and transmitted using a variety of computer-readablemedia.

A computer-readable medium (also referred to as a processor-readablemedium) includes any non-transitory (e.g., tangible) medium thatparticipates in providing data (e.g., instructions) that may be read bya computer (e.g., by a processor of a computer). Such a medium may takemany forms, including, but not limited to, non-volatile media andvolatile media. Non-volatile media may include, for example, optical ormagnetic disks and other persistent memory. Volatile media may include,for example, dynamic random-access memory (DRAM), which typicallyconstitutes a main memory. Such instructions may be transmitted by oneor more transmission media, including coaxial cables, copper wire andfiber optics, including the wires that comprise a system bus coupled toa processor of a computer. Common forms of computer-readable mediainclude, for example, a floppy disk, a flexible disk, hard disk,magnetic tape, any other magnetic medium, a CD-ROM, DVD, any otheroptical medium, punch cards, paper tape, any other physical medium withpatterns of holes, a RAM, a PROM, an EPROM, a FLASH-EEPROM, any othermemory chip or cartridge, or any other medium from which a computer canread.

Databases, data repositories or other data stores described herein mayinclude various kinds of mechanisms for storing, accessing, andretrieving various kinds of data, including a hierarchical database, aset of files in a file system, an application database in a proprietaryformat, a relational database management system (RDBMS), etc. Each suchdata store is generally included within a computing device employing acomputer operating system such as one of those mentioned above, and areaccessed via a network in any one or more of a variety of manners. Afile system may be accessible from a computer operating system, and mayinclude files stored in various formats. An RDBMS generally employs theStructured Query Language (SQL) in addition to a language for creating,storing, editing, and executing stored procedures, such as the PL/SQLlanguage mentioned above.

In some examples, system elements may be implemented ascomputer-readable instructions (e.g., software) on one or more computingdevices (e.g., such as computer 22), stored on computer readable mediaassociated therewith (e.g., disks, memories, etc.). A computer programproduct may comprise such instructions stored on computer readable mediafor carrying out the functions described herein.

The processor is implemented via circuits, chips, or other electroniccomponent and may include one or more microcontrollers, one or morefield programmable gate arrays (FPGAs), one or more application specificcircuits ASICs), one or more digital signal processors (DSPs), one ormore customer integrated circuits, etc. The processor may be programmedto process the sensor data. As described herein, the processor instructsvehicle components to actuate in accordance with the sensor data.

The memory (or data storage device) is implemented via circuits, chipsor other electronic components and can include one or more of read onlymemory (ROM), random-access memory (RAM), flash memory, electricallyprogrammable memory (EPROM), electrically programmable and erasablememory (EEPROM), embedded MultiMediaCard (eMMC), a hard drive, or anyvolatile or non-volatile media etc. The memory may store data collectedfrom sensors.

The disclosure has been described in an illustrative manner, and it isto be understood that the terminology which has been used is intended tobe in the nature of words of description rather than of limitation. Manymodifications and variations of the present disclosure are possible inlight of the above teachings, and the disclosure may be practicedotherwise than as specifically described.

1. A method for determining whether to execute a power transfer unit(PTU) maintenance task, comprising: determining at least one of thefollowing: a communication error, a read-memory error, or an absence ofa PTU shift between a two-wheel drive (2WD) mode and an all-wheel drive(AWD) mode for a threshold amount of vehicle operation; determining thata vehicle ignition state is not in a RUN state; and based on bothdeterminations, executing the task.
 2. The method of claim 1, whereinthe task comprises moving one or more components of an actuator of thePTU.
 3. The method of claim 2, wherein the task comprises moving adriving member of the actuator of the PTU relative to a driven member.4. The method of claim 1, wherein the threshold amount of vehicleoperation comprises measuring vehicle travel distance or a globaloperation time.
 5. The method of claim 4, further comprising, based onexecuting the task: resetting a distance counter that measures vehiclemileage, resetting a counter associated with the global operation time,or both.
 6. The method of claim 1, further comprising: executing thetask during an extended_ON mode which provides electrical power for acomputer processor when the ignition state is an OFF state.
 7. Themethod of claim 1, further comprising: aborting the task based ondetermining a change in the ignition state or a PTU failure mode.
 8. Themethod of claim 7, further comprising: storing an indication of a PTUmaintenance event in non-volatile memory so that the task may beexecuted in response to a subsequent ignition cycle.
 9. The method ofclaim 1, wherein the communication error comprises one of: a connectionfailure, a node failure, or an error message over a communicationnetwork connection.
 10. The method of claim 1, wherein the read-memoryerror comprises one of: an inability of a computer processor to readdata stored in computer memory; a memory error message indicating thatat least a portion of the computer memory is corrupted; or reading datafrom the computer memory, and determining that one or more data valuesare out-of-range.
 11. The method of claim 1, wherein the absence of thePTU shift between the 2WD mode and the AWD mode for the threshold amountof vehicle operation comprises one of: (a) comparing a distance countervalue (ΔOV) with a mileage threshold, wherein the distance counter value(ΔOV) comprises a difference of a current odometer value (COV) and areset odometer value (ROV); or (b) comparing a global operation timevalue (ΔGOTV) with a global operation time threshold, wherein the globaloperation time value (ΔGOTV) comprises a difference of a current globaloperation time value (CGOTV) and a reset global operation time value(RGOTV).
 12. The method of claim 1, wherein the absence of the PTU shiftbetween the 2WD mode and the AWD mode for the threshold amount ofvehicle operation comprises: incrementing a counter in response to anyof the following: (a) determining that a requested driver mode is the2WD mode, determining that the PTU is in the AWD mode, andunsuccessfully attempting to move the PTU to the 2WD mode; (b)determining that the requested driver mode is the AWD mode, determiningthat the PTU is in the 2WD mode, and unsuccessfully attempting to movethe PTU to the AWD mode; (c) determining that the requested driver modeis the 2WD mode and determining that the PTU is already in the 2WD mode;or (d) determining that the requested driver mode is the AWD mode anddetermining that the PTU is already in the AWD mode.
 13. The method ofclaim 1, wherein the PTU is coupled to a manual transmission.
 14. Asystem for performing a power transfer unit (PTU) maintenance task,comprising: a processor; and memory storing instructions executable bythe processor, the instructions comprising, to: determine an absence ofa PTU shift for a distance threshold or a global operation timethreshold; then, determine that a vehicle ignition state is not in a RUNstate; and then, execute the task.
 15. The system of claim 14, whereinthe instructions further comprise, to: prior to determining that theignition state is not the RUN state, determine a PTU shift between atwo-wheel drive (2WD) mode and an all-wheel drive (AWD) mode; and then,reset at least one counter associated with the distance threshold or theglobal operation time threshold.
 16. The system of claim 14, wherein thetask comprises moving one or more components of an actuator of the PTUbetween a connected and disconnected state.
 17. The system of claim 14,wherein the instructions further comprise, to: while the ignition stateis the RUN state, determine a communication error or a read-memoryerror; then, determine that the ignition state is not in the RUN stateand execute the task.
 18. The system of claim 14, wherein theinstructions further comprise, to: execute the task during anextended_ON mode which provides electrical power for the processor whenthe ignition state is an OFF state.
 19. The system of claim 14, whereinthe absence of the PTU shift for the distance threshold or the globaloperation time threshold further comprises an instruction, to: incrementa counter in response to any of the following: (e) determining that arequested driver mode is a two-wheel drive (2WD) mode, determining thatthe PTU is in an all-wheel drive (AWD) mode, and unsuccessfullyattempting to move the PTU to the 2WD mode; (f) determining that therequested driver mode is the AWD mode, determining that the PTU is inthe 2WD mode, and unsuccessfully attempting to move the PTU to the AWDmode; (g) determining that the requested driver mode is the 2WD mode anddetermining that the PTU is already in the 2WD mode; or (h) determiningthat the requested driver mode is the AWD mode and determining that thePTU is already in the AWD mode.
 20. The system of claim 14, furthercomprising the PTU and a computer that comprises the processor andmemory.